Add implementation_url to WritableStream in Safari #7417
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds an implementation_url value for WritableStream in Safari and iOS Safari, per https://trac.webkit.org/changeset/266172/webkit, which says > Implementation is now ready and is up to date with the latest specification. As mdn#6873 (comment) notes, that change means this feature shipped in at least TP 114 and probably was also in since TP 113.
github-actions
bot
added
the
data:api 🐇
|
I think this MR was superseded by #10129, so is probably closable. |
Yep — thanks, closing |
sideshowbarker
deleted the
sideshowbarker/WritableStream-add-implementation_url
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds an
implementation_urlvalue forWritableStreamin Safari and iOS Safari, per https://trac.webkit.org/changeset/266172/webkit, which says:As #6873 (comment) notes, that change means this feature shipped in at least TP 114 and probably was also in since TP 113.
Note that this is expected to fail CI unless/until #7396 gets merged